BBS Toolkit/BBS Toolkit.iso/spitfire/ck4pst11.zip/CK4PEST.DOC

Text File | 1992-12-31 | 17KB | 415 lines

                 ┌────────────────────────────────────────────┐
                 │                 CK4PEST V1.1               │▒
                 └────────────────────────────────────────────┘▒
                   ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
                                Release: 12/26/92

                         -=  Share ware By Arrowhead  =-
                                 Steven Elwood
                               Arrowhead Analysis
                                 1019 Darter Rd.
                                 Helena, Montana
                                      59601

┌──────────────────┐
│       Files      │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

       The following files are contained in the CK4PEST archive:

       CK4PEST.EXE             The executable (required)
       CK4CONFI.EXE            Executable to prepare .CFG file
       FILE_ID.DIZ             A short description of the program.
       CK4PEST.CFG             The configuration file (sample included)
       CK4TIME.EXE             Date-stamping program (required)
       CK4PEST.BSV             ANSI Screen For CK4PEST.EXE (required)
       CK4CONFI.BSV            ANSI Screen For CK4CONFI.EXE (required)
       CK4PEST.REG             Registration form
       CK4PEST.KEY             (Provided to registered users only)
       DTR.COM                 Data-Terminal-Ready Routine (required)

       In addition, the program generates CK4PEST.DAT and CK4PEST.LOG.

┌──────────────────┐
│   Requirements   │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

       * Spitfire BBS.

       * Your system must hold the correct time/date.

       * A copy of PKUNZIP.EXE.

┌──────────────────┐
│    Background    │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒


       Some sysops are troubled by callers who log on, use up all
       their allotted time, drop the link and then call back for
       a second go-around.  This kind of caller-behavior can be
       irritating.  Spitfire, unfortunately, doesn't allow the
       sysop to establish the number-of-logins per-caller and so
       the only Spitfire remedy is to set ALL callers down to 2
       or 3 (or whatever).  Nor does Spitfire have the ability to
       check for 'successive-caller syndrome'.  CK4PEST does!

       CK4PEST allows the sysop considerably more control over this
       type of problem caller.  Through the configuration file, the
       sysop is able to establish a MINIMUM number of minutes
       which must elapse successive reconnects by the same caller.

┌──────────────────┐
│    What It Does  │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒


       CK4PEST keeps a record of the last caller's name and the date/
       time of his/her last call.  When a new caller connects and logs
       in, CK4PEST compares the new caller's name/time/date to the data
       logged (CK4PEST.DAT) by the last caller.

       If the new caller's name is not the same as the last caller's,
       CK4PEST does nothing.  If the last caller's name is the same
       as the current caller, then CK4PEST looks at the present date/
       time and compares that information to the current date/time.

       If the date is the same, CK4PEST determines the number of
       minutes since this caller's last call and compares that number
       to the "threshold" value established by the sysop in the
       CK4PEST.CFG file.

       If the number of elapsed minutes EXCEEDS the number of "threshold"
       minutes, the caller continues on with the BBS.  In other words,
       more time has elapsed since his/her last call than the sysop is
       concerned with as a "threshold" value.

       If, however, the number of elapsed minutes since the last call is
       equal to or less than the number of "threshold" minutes established
       by the CK4PEST.CFG file, the caller is sent a string of text
       (configured by the sysop in CK4PEST.CFG) and the caller is
       disconnected.

       A new .DAT file is always created with a new time-stamp.

┌──────────────────┐
│      Features    │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

       CK4PEST is quick.  It does quite a bit of analysis in a very
       short time period.

       CK4PEST will work with any COM port you have configured for
       Spitfire.

       CK4PEST will honor any existing locked serial speed found.

       CK4PEST recognizes local-console logins and the sysop will
       not be 'snagged' by CK4PEST.

       CK4PEST contains a separate program to assist you in developing
       the necessary configuration file.

       CK4PEST recognizes and ignores EXEMPT security levels you
       specify.

       CK4PEST provides the sysop with complete control over which
       callers get 'snagged', how long the program allows successive
       callers to make repeated calls, and the "shame-on-you" phrase
       sent to 'snagged' callers.

       The program recognizes those callers who are not validated
       with increased security levels as a result of successfully
       completing automatic call back validation (if you use one).
       These callers often link several times until such time as
       they become validated callers.  The program recognizes,
       therefore, the LOWEST level VALIDATED security levels you
       use.  When a caller links who is NOT yet validated, CK4PEST
       takes no action against him/her.

       This is a shareware version.  It is NOT crippled in any way.

       CK4PEST generates its own log in the same sub directory where the
       other CK4PEST files are located (CK4PEST.LOG).  The log will
       reveal the 'snagged' caller's name, both the time he/she
       was dumped and the time of his/her previous link, and the
       number of minutes between the caller's successive calls.
       Or you may configure the log file to be appended to any other
       text file -- or disable logging altogether.

       Considerable error-checking is incorporated.

┌──────────────────┐
│   Installation   │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

       1.  Create a CK4PEST directory off your main Spitfire
           sub directory.  Empty the contents of CK4PEST.ZIP there.

       2.  Extract CK4PEST.ZIP into directory;

       3.  Edit your SFLOGON.BAT file to include the following lines:

                            CD <path to CK4PEST sub>
                            CK4PEST.EXE
                            CD <path back to SF>

       4.  Edit your SFINIT.BAT file to include the following lines:
                             CD <path to CK4PEST sub>
                             CK4TIME.EXE
                             CD <path back to SF>

       4.  Run CK4CONFI.EXE.  That program will set up a .CFG file
           for you.  Read the screens CAREFULLY!  You may also create
           one with an ASCII editor as follows:

           * Line 1 = The number of "threshold" minutes which you
                      wish to use (ie: 30).  If a caller called before
                      and calls back, he must wait <threshold> minutes
                      or longer or he/she will be dumped.

           * Line 2 = Logging option.  You may enter any one of the
                      following choices:

                      1) NONE  -  disables logging;
                      2) DEFAULT  -  logging will be written to CK4PEST.LOG;
                      3) <any path+filename> which might include
                         D:\SF\CALLERS.TMP or D:\SF\WORK\CALLERS.LOG,
                         or whatever you prefer.

           * Line 3 = The path to the CK4PEST files.  BE SURE TO
                      KEEP THE TRAILING BACK SLASH IN THERE!

                      Example: D:\SF\CK4PEST\

           * Line 4 = The path to your main Spitfire directory.  BE
                      SURE TO KEEP THE TRAILING BACK SLASH IN THERE!

                      Example: D:\SF\

           * Line 5 = A number which represents the LOWEST LEVEL
                      (a security level number) of VALIDATED callers on
                      your system.

                      As example, if your lowest VALIDATED callers are
                      security level 10, then enter than number here on
                      line 3.

                      All callers who connect with security levels LOWER
                      than this number are assumed to be non-validated
                      callers and will NOT be affected by CK4PEST.

             NOTE!:   Enter NONE to disable this feature.
                      Entering NONE will inform CK4PEST that you, the
                      sysop, either don't use validation or you wish to
                      disregard the "non-validated caller" status.  ALL
                      callers then, (except those EXEMPT callers in line
                      6, below) will be analyzed by CK4PEST.

           * Line 6 = This line will contain the SECURITY LEVELS of those
                      callers you wish to EXEMPT from CK4PEST.  This line
                      REQUIRES 6 entries.  (If you use the included file
                      CK4CONFI.EXE, the CFG file will be prepared properly).

                      Entries must be either a number or the word NONE.

                      Examples:

                      NONE,NONE,NONE,NONE,NONE,NONE
                                                    Disables EXEMPT callers.

                      40,50,NONE,NONE,NONE,NONE
                      ^^ ^^ ----------------------- Exempts callers with
                                                    security levels 40
                                                    and 50.

                      40,45,55,65,70,90
                      ^^ ^^ ^^ ^^ ^^ ^^ ----------- Exempts callers with
                                                    security levels 40, 45,
                                                    55, 65, 70 and 90.

             NOTE!:   The COMMA MUST be placed between each security
                      level as a delimiter.

           * Line 7 = The phrase you wish to send to callers (pests)
                      who are trapped by this program.

                      Example:

                      You just called!  Give others a chance!

           * Line 8 = The second line in a phrase (optional) you wish
                      to send to callers trapped by this program.

                      Example: Try again in 30-45 minutes!

             NOTE!:   If you do NOT wish to use this line, enter NONE to
                      disable it.  In such cases, only Line 7 (above)
                      will be sent to the 'snagged' caller.

           Delete any/all blank lines at the end of this ASCII file.

           That's all there is to it!

           Here are some examples:

        *  In this example, the threshold is 30 minutes, the logging will
           be done to the DEFAULT CK4PEST.LOG file (in the CK4PEST
           sub directory), the path to the CK4PEST files is C:\SF\CK4PEST,
           the path to the Spitfire sub directory is C:\SF\, your LOWEST
           VALIDATED SECURITY LEVEL is 5, all security level 40 and 50
           callers are EXEMPT and the phrase (2 lines) sent to the
           'snagged' caller:

           30
           DEFAULT
           C:\SF\CK4PEST\
           C:\SF\
           5
           40,50,NONE,NONE,NONE,NONE  (total of 6 entries on this line!)
           Please give others a chance -- disconnecting!
           Try back again later!

        *  In this example, the threshold is 15 minutes, logging will be
           APPENDED to the D:\SF\CALLERS.TMP file, the path to your
           CK4PEST files is D:\SF\CK4PEST, the path to the Spitfire sub
           directory is D:\SF\, the lowest VALIDATED security level is 10,
           the phrase sent to the 'snagged' caller (only 1 line - the
           second line has been disabled with the NONE statement):

           15
           D:\SF\CALLERS.TMP
           D:\SF\CK4PEST\
           D:\SF\
           50,NONE,NONE,NONE,NONE,NONE (total of 6 entries on this line!)
           Give us a break!  Call back later!
           NONE

        *  In this example, the threshold is 30 minutes, logging will be
           disabled, the path to the CK4PEST files is C:\SF\, the path
           to the Spitfire sub directory is C:\SF\, there are no validated
           callers, there are NO EXEMPT callers, the phrase sent to the
           'snagged' caller (only 1 line - the second line has been disabled
           with the NONE statement):

           30
           NONE
           C:\SF\
           C:\SF\
           NONE
           NONE NONE NONE NONE NONE NONE
           What's the problem?  You were just online here!
           NONE

┌──────────────────┐
│   CUSTOMIZATION  │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

           You can alter any of the values contained in the CK4PEST.CFG
           file.

           You can alter the look of the screens.  Use of TheDraw program
           will permit you to fabricate your own screens and save them in
           the BSAVE format -- that's why the screens provided were
           created with TheDraw.

           Source code is not provided nor are any changes or
           alterations to the executable programs permitted.

           Note:  No screens are sent to the 'snagged' caller.  Just
           text.

┌──────────────────┐
│       Plans      │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

           Multi-node use hasn't been tested.  There WOULD be a
           conflict unless separate copies of CK4PEST are run in
           SEPARATE file areas.  Multi-node enhancements are
           planned;

           Plans to pull two of the existing modules into the main
           body of the program.

           Options to track more than just the last 1 caller to
           include up to three or more.

┌──────────────────┐
│    DISCLAIMER    │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒


           Steven Elwood shall not be liable to any users of CK4PEST for
           any damages, including any lost profits, lost savings or other
           incidental or consequential damages arising out of the use or
           inability to use these programs, or for any claim by any other
           party.  Total responsibility for use herein lies with the user.

           This CK4PEST software is being distributed as "SHARE WARE". You
           may freely distribute this program to other sysops, and you are
           encouraged to do so. You may try out CK4PEST for a trial period
           of 30 (thirty) days. If you continue to use CK4PEST, fill out the
           CK4PEST.REG registration form and mail appropriate payment to
           the author of this software.

           CK4PEST may not be distributed by software vendors without
           expressed written consent of this author.


┌──────────────────┐
│   REGISTRATION   │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

           There is NO registration required.  Consider this a freebie.

           If you are inclined to support future efforts of this program
           CK4PEST.REG is contained in the archive package.  It includes
           a quik-n-dirty registration application along with the mailing
           address.  Registration is $5.00.  The CK4PEST screen on
           registered copies discloses the sysop's registration number
           and a registered keyfile is provided.

           The latest version is always on my support BBS at:

           WestNet BBS - [phone]

           Or you can address mail to me, Steven Elwood, at CircuitNET
           node# 406000


┌──────────────────┐
│ ACKNOWLEDGEMENTS │▒
└──────────────────┘▒
  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒

           * SPITFIRE is a trademark of Buffalo Creek Software, copyright
             by Mike Woltz.

           * PKUNZIP is copyright PKWare and Phil Katz.

           * CK4PEST is share ware (all rights reserved) by Steven Elwood
             and Arrowhead Analysis.

           * The following SysOps have aided in the beta-testing of this
             program:

             Phil Helms - Milo's Bloom County BBS - Great Falls, MT
             Phone: [phone]

             Cliff Ayers - Bloom II - Bill's Revenge BBS - Great Falls, MT
             Phone: [phone]

             Their help is immensely appreciated.